Device, method, and graphical user interface for navigation of information in a map-based interface

ABSTRACT

A device with a display and a touch-sensitive surface: displays a geographic map in a first mode of an application, the geographic map including a plurality of landmarks, the geographic map being displayed at a first magnification level; detects a first input, the first input including a first finger contact at a location on the touch-sensitive surface that corresponds to a first landmark on the display; in response to detecting the first input: when the first input does not satisfy one or more predefined mode-change conditions, changes the magnification level in accordance with the first input and remains in the first mode; and when the first input satisfies the mode-change conditions, selects the first landmark and enters a second mode of the application; while in the second mode, detects a second input; and, in response to detecting the second input, displays information about the first landmark.

RELATED APPLICATION

This application is a continuation of U.S. Nonprovisional applicationSer. No. 16/256,791, filed Jan. 24, 2019, which is a continuation ofU.S. Nonprovisional application Ser. No. 13/536,650, filed Jun. 28, 2012(now U.S. Pat. No. 10,191,641, issued Jan. 29, 2019), which claimspriority to U.S. Provisional Application Ser. No. 61/581,613, filed Dec.29, 2011, all of which are incorporated herein by reference in theirentirety.

TECHNICAL FIELD

This relates generally to electronic devices with touch-sensitivesurfaces, including but not limited to electronic devices withtouch-sensitive surfaces that navigate through information in amap-based interface.

BACKGROUND

The use of touch-sensitive surfaces as input devices for computers andother electronic computing devices has increased significantly in recentyears. Exemplary touch-sensitive surfaces include touch pads and touchscreen displays. Such surfaces are widely used to manipulate userinterface objects on a display.

Exemplary manipulations include interacting with a map application orinterface to access various pieces of information. But existing methodsfor accessing information in a map application or interface arecumbersome and inefficient. For example, there may be many pieces,types, and/or levels of information for a single location on a map. Butsuch information is presented in ways that do not facilitate cognitiveassociation with the single location and that do not facilitate smoothnavigation between the pieces, types, and/or levels of information. Thiscreates a significant cognitive burden on a user and lessens the utilityof the information. In addition, existing methods take longer thannecessary to navigate through the information, thereby wasting energy.This latter consideration is particularly important in battery-operateddevices.

SUMMARY

Accordingly, there is a need for electronic devices with faster, moreefficient methods and interfaces for navigating through information in amap-based interface. Such methods and interfaces may complement orreplace conventional methods for navigating through information in amap-based interface. Such methods and interfaces reduce the cognitiveburden on a user and produce a more efficient human-machine interface.For battery-operated devices, such methods and interfaces conserve powerand increase the time between battery charges.

The above deficiencies and other problems associated with userinterfaces for electronic devices with touch-sensitive surfaces arereduced or eliminated by the disclosed devices. In some embodiments, thedevice is a desktop computer. In some embodiments, the device isportable (e.g., a notebook computer, tablet computer, or handhelddevice). In some embodiments, the device has a touchpad. In someembodiments, the device has a touch-sensitive display (also known as a“touch screen” or “touch screen display”). In some embodiments, thedevice has a graphical user interface (GUI), one or more processors,memory and one or more modules, programs or sets of instructions storedin the memory for performing multiple functions. In some embodiments,the user interacts with the GUI primarily through finger contacts andgestures on the touch-sensitive surface. In some embodiments, inaddition to mapping, the functions may include image editing, drawing,presenting, word processing, website creating, disk authoring,spreadsheet making, game playing, telephoning, video conferencing,e-mailing, instant messaging, workout support, digital photographing,digital videoing, web browsing, digital music playing, and/or digitalvideo playing. Executable instructions for performing these functionsmay be included in a non-transitory computer readable storage medium orother computer program product configured for execution by one or moreprocessors.

In accordance with some embodiments, a method is performed at anelectronic device with a display and a touch-sensitive surface. Themethod includes: displaying a geographic map in a first mode of anapplication on the display, the geographic map including a plurality oflandmarks, the geographic map being displayed at a first magnificationlevel in a range of magnification levels; detecting a first input on thetouch-sensitive surface, the first input including a first fingercontact at a location on the touch-sensitive surface that corresponds toa first landmark on the display; in response to detecting the firstinput on the touch-sensitive surface: when the first input does notsatisfy one or more predefined mode-change conditions, changing themagnification level of the geographic map in accordance with the firstinput and remaining in the first mode of the application; and when thefirst input satisfies the one or more predefined mode-change conditions,selecting the first landmark and entering a second mode of theapplication that is distinct from the first mode; while in the secondmode of the application, detecting a second input on the touch-sensitivesurface; and, in response to detecting the second input on thetouch-sensitive surface, displaying information about the firstlandmark.

In accordance with some embodiments, an electronic device includes adisplay, a touch-sensitive surface, one or more processors, memory, andone or more programs. The one or more programs are stored in the memoryand configured to be executed by the one or more processors. The one ormore programs include instructions for: displaying a geographic map in afirst mode of an application on the display, the geographic mapincluding a plurality of landmarks, the geographic map being displayedat a first magnification level in a range of magnification levels;detecting a first input on the touch-sensitive surface, the first inputincluding a first finger contact at a location on the touch-sensitivesurface that corresponds to a first landmark on the display; in responseto detecting the first input on the touch-sensitive surface: when thefirst input does not satisfy one or more predefined mode-changeconditions, changing the magnification level of the geographic map inaccordance with the first input and remaining in the first mode of theapplication; and when the first input satisfies the one or morepredefined mode-change conditions, selecting the first landmark andentering a second mode of the application that is distinct from thefirst mode; while in the second mode of the application, detecting asecond input on the touch-sensitive surface; and, in response todetecting the second input on the touch-sensitive surface, displayinginformation about the first landmark.

In accordance with some embodiments, a computer readable storage mediumhas stored therein instructions which when executed by an electronicdevice with a display and a touch-sensitive surface, cause the deviceto: display a geographic map in a first mode of an application on thedisplay, the geographic map including a plurality of landmarks, thegeographic map being displayed at a first magnification level in a rangeof magnification levels; detect a first input on the touch-sensitivesurface, the first input including a first finger contact at a locationon the touch-sensitive surface that corresponds to a first landmark onthe display; in response to detecting the first input on thetouch-sensitive surface: when the first input does not satisfy one ormore predefined mode-change conditions, change the magnification levelof the geographic map in accordance with the first input and remain inthe first mode of the application; and when the first input satisfiesthe one or more predefined mode-change conditions, select the firstlandmark and enter a second mode of the application that is distinctfrom the first mode; while in the second mode of the application, detecta second input on the touch-sensitive surface; and, in response todetecting the second input on the touch-sensitive surface, displayinformation about the first landmark.

In accordance with some embodiments, a graphical user interface on anelectronic device with a display, a touch-sensitive surface, a memory,and one or more processors to execute one or more programs stored in thememory includes a geographic map in a first mode of an application, thegeographic map including a plurality of landmarks, the geographic mapbeing displayed at a first magnification level in a range ofmagnification levels. In response to detection of a first input on thetouch-sensitive surface, the first input including a first fingercontact at a location on the touch-sensitive surface that corresponds toa first landmark: when the first input does not satisfy one or morepredefined mode-change conditions, the magnification level of thegeographic map is changed in accordance with the first input and thegeographic map remains in the first mode of the application; and whenthe first input satisfies the one or more predefined mode-changeconditions, the first landmark is selected and a second mode of theapplication that is distinct from the first mode is entered; and, inresponse to detection of a second input on the touch-sensitive surfacewhile in the second mode of the application, information about the firstlandmark is displayed.

In accordance with some embodiments, an electronic device includes: adisplay; a touch-sensitive surface; means for displaying a geographicmap in a first mode of an application on the display, the geographic mapincluding a plurality of landmarks, the geographic map being displayedat a first magnification level in a range of magnification levels; meansfor detecting a first input on the touch-sensitive surface, the firstinput including a first finger contact at a location on thetouch-sensitive surface that corresponds to a first landmark on thedisplay; means, responsive to detecting the first input on thetouch-sensitive surface, for, when the first input does not satisfy oneor more predefined mode-change conditions, changing the magnificationlevel of the geographic map in accordance with the first input andremaining in the first mode of the application; means, responsive todetecting the first input on the touch-sensitive surface, for, when thefirst input satisfies the one or more predefined mode-change conditions,selecting the first landmark and entering a second mode of theapplication that is distinct from the first mode; means for, while inthe second mode of the application, detecting a second input on thetouch-sensitive surface; and, means, responsive to detecting the secondinput on the touch-sensitive surface, for displaying information aboutthe first landmark.

In accordance with some embodiments, an information processing apparatusfor use in an electronic device with a display and a touch-sensitivesurface includes: means for displaying a geographic map in a first modeof an application on the display, the geographic map including aplurality of landmarks, the geographic map being displayed at a firstmagnification level in a range of magnification levels; means fordetecting a first input on the touch-sensitive surface, the first inputincluding a first finger contact at a location on the touch-sensitivesurface that corresponds to a first landmark on the display; means,responsive to detecting the first input on the touch-sensitive surface,for, when the first input does not satisfy one or more predefinedmode-change conditions, changing the magnification level of thegeographic map in accordance with the first input and remaining in thefirst mode of the application; means, responsive to detecting the firstinput on the touch-sensitive surface, for, when the first inputsatisfies the one or more predefined mode-change conditions, selectingthe first landmark and entering a second mode of the application that isdistinct from the first mode; means for, while in the second mode of theapplication, detecting a second input on the touch-sensitive surface;and, means, responsive to detecting the second input on thetouch-sensitive surface, for displaying information about the firstlandmark.

In accordance with some embodiments, an electronic device includes adisplay unit configured to display a geographic map in a first mode ofan application on the display unit, the geographic map including aplurality of landmarks, the geographic map being displayed at a firstmagnification level in a range of magnification levels; atouch-sensitive surface unit configured to receive inputs and gestures;and a processing unit coupled to the display unit and thetouch-sensitive surface unit. The processing unit is configured to:detect a first input on the touch-sensitive surface unit, the firstinput including a first finger contact at a location on thetouch-sensitive surface unit that corresponds to a first landmark on thedisplay unit; in response to detecting the first input on thetouch-sensitive surface unit: when the first input does not satisfy oneor more predefined mode-change conditions, change the magnificationlevel of the geographic map in accordance with the first input andremain in the first mode of the application; and when the first inputsatisfies the one or more predefined mode-change conditions, select thefirst landmark and enter a second mode of the application that isdistinct from the first mode; while in the second mode of theapplication, detect a second input on the touch-sensitive surface unit;and, in response to detecting the second input on the touch-sensitivesurface unit, enable display of information about the first landmark.

Thus, electronic devices with displays and touch-sensitive surfaces areprovided with faster, more efficient methods and interfaces fornavigating through information in a map-based interface, therebyincreasing the effectiveness, efficiency, and user satisfaction withsuch devices. Such methods and interfaces may complement or replaceconventional methods for navigating through information in a map-basedinterface.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the aforementioned embodiments of theinvention as well as additional embodiments thereof, reference should bemade to the Description of Embodiments below, in conjunction with thefollowing drawings in which like reference numerals refer tocorresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIGS. 5A-5K illustrate exemplary user interfaces for navigating throughinformation in a map-based interface in accordance with someembodiments.

FIGS. 6A-6D are flow diagrams illustrating a method of navigatingthrough information in a map-based interface in accordance with someembodiments.

FIG. 7 is a functional block diagram of an electronic device inaccordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

Many electronic devices are capable of displaying geographic maps in amap application or mapping interface. Such maps and mapping interfacesallow users the opportunity to find information about landmarks in themaps. However, a landmark may have a wide variety of information thatcan be displayed, and current methods of presenting and navigatingthrough such information are cumbersome. The embodiments below describemethods for navigating through various pieces, types, and/or levels ofinformation for a landmark on a map. When a user performs a gesture on alandmark in a map interface and one or more conditions are satisfied,the map interface changes from a map viewing mode to a landmarkinformation mode. The user performs a gesture (e.g., a depinch gesture)on the landmark while in the landmark information mode to bring upinformation about that landmark. The user may repeat the gesture tobring up different information about the landmark, or perform adifferent gesture to change back to the map viewing mode. This gives theuser a more efficient way to navigate on a map and bring up varioustypes of information about a landmark on the map using simple gestures.

Below, FIGS. 1A-1B, 2, 3, and 7 provide a description of exemplarydevices. FIGS. 4A-4B and 5A-5K illustrate exemplary user interfaces fornavigating through information in a map-based interface. FIGS. 6A-6D areflow diagrams illustrating a method of navigating through information ina map-based interface. The user interfaces in FIGS. 5A-5K are used toillustrate the processes in FIGS. 6A-6D.

Exemplary Devices

Reference will now be made in detail to embodiments, examples of whichare illustrated in the accompanying drawings. In the following detaileddescription, numerous specific details are set forth in order to providea thorough understanding of the present invention. However, it will beapparent to one of ordinary skill in the art that the present inventionmay be practiced without these specific details. In other instances,well-known methods, procedures, components, circuits, and networks havenot been described in detail so as not to unnecessarily obscure aspectsof the embodiments.

It will also be understood that, although the terms first, second, etc.may be used herein to describe various elements, these elements shouldnot be limited by these terms. These terms are only used to distinguishone element from another. For example, a first contact could be termed asecond contact, and, similarly, a second contact could be termed a firstcontact, without departing from the scope of the present invention. Thefirst contact and the second contact are both contacts, but they are notthe same contact.

The terminology used in the description of the invention herein is forthe purpose of describing particular embodiments only and is notintended to be limiting of the invention. As used in the description ofthe invention and the appended claims, the singular forms “a”, “an” and“the” are intended to include the plural forms as well, unless thecontext clearly indicates otherwise. It will also be understood that theterm “and/or” as used herein refers to and encompasses any and allpossible combinations of one or more of the associated listed items. Itwill be further understood that the terms “includes,” “including,”“comprises,” and/or “comprising,” when used in this specification,specify the presence of stated features, integers, steps, operations,elements, and/or components, but do not preclude the presence oraddition of one or more other features, integers, steps, operations,elements, components, and/or groups thereof.

As used herein, the term “if” may be construed to mean “when” or “upon”or “in response to determining” or “in response to detecting,” dependingon the context. Similarly, the phrase “if it is determined” or “if [astated condition or event] is detected” may be construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, California. Other portableelectronic devices, such as laptops or tablet computers withtouch-sensitive surfaces (e.g., touch screen displays and/or touchpads), may also be used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touch pad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device may include one or moreother physical user-interface devices, such as a physical keyboard, amouse and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that may be executed on the device may use atleast one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the device maybe adjusted and/or varied from one application to the next and/or withina respective application. In this way, a common physical architecture(such as the touch-sensitive surface) of the device may support thevariety of applications with user interfaces that are intuitive andtransparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive displays 112 inaccordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience, and may also be knownas or called a touch-sensitive display system. Device 100 may includememory 102 (which may include one or more computer readable storagemediums), memory controller 122, one or more processing units (CPU's)120, peripherals interface 118, RF circuitry 108, audio circuitry 110,speaker 111, microphone 113, input/output (I/O) subsystem 106, otherinput or control devices 116, and external port 124. Device 100 mayinclude one or more optical sensors 164. These components maycommunicate over one or more communication buses or signal lines 103.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 may have more orfewer components than shown, may combine two or more components, or mayhave a different configuration or arrangement of the components. Thevarious components shown in FIG. 1A may be implemented in hardware,software, or a combination of both hardware and software, including oneor more signal processing and/or application specific integratedcircuits.

Memory 102 may include high-speed random access memory and may alsoinclude non-volatile memory, such as one or more magnetic disk storagedevices, flash memory devices, or other non-volatile solid-state memorydevices. Access to memory 102 by other components of device 100, such asCPU 120 and the peripherals interface 118, may be controlled by memorycontroller 122.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data.

In some embodiments, peripherals interface 118, CPU 120, and memorycontroller 122 may be implemented on a single chip, such as chip 104. Insome other embodiments, they may be implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 may include well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 may communicate with networks, such as the Internet, alsoreferred to as the World Wide Web (WWW), an intranet and/or a wirelessnetwork, such as a cellular telephone network, a wireless local areanetwork (LAN) and/or a metropolitan area network (MAN), and otherdevices by wireless communication. The wireless communication may useany of a plurality of communications standards, protocols andtechnologies, including but not limited to Global System for MobileCommunications (GSM), Enhanced Data GSM Environment (EDGE), high-speeddownlink packet access (HSDPA), high-speed uplink packet access (HSUPA),wideband code division multiple access (W-CDMA), code division multipleaccess (CDMA), time division multiple access (TDMA), Bluetooth, WirelessFidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g and/orIEEE 802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocolfor e-mail (e.g., Internet message access protocol (IMAP) and/or postoffice protocol (POP)), instant messaging (e.g., extensible messagingand presence protocol (XMPP), Session Initiation Protocol for InstantMessaging and Presence Leveraging Extensions (SIMPLE), Instant Messagingand Presence Service (IMPS)), and/or Short Message Service (SMS), or anyother suitable communication protocol, including communication protocolsnot yet developed as of the filing date of this document.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data may be retrievedfrom and/or transmitted to memory 102 and/or RF circuitry 108 byperipherals interface 118. In some embodiments, audio circuitry 110 alsoincludes a headset jack (e.g., 212, FIG. 2 ). The headset jack providesan interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 may include display controller 156 andone or more input controllers 160 for other input or control devices.The one or more input controllers 160 receive/send electrical signalsfrom/to other input or control devices 116. The other input controldevices 116 may include physical buttons (e.g., push buttons, rockerbuttons, etc.), dials, slider switches, joysticks, click wheels, and soforth. In some alternate embodiments, input controller(s) 160 may becoupled to any (or none) of the following: a keyboard, infrared port,USB port, and a pointer device such as a mouse. The one or more buttons(e.g., 208, FIG. 2 ) may include an up/down button for volume control ofspeaker 111 and/or microphone 113. The one or more buttons may include apush button (e.g., 206, FIG. 2 ).

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output may includegraphics, text, icons, video, and any combination thereof (collectivelytermed “graphics”). In some embodiments, some or all of the visualoutput may correspond to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor or set of sensorsthat accepts input from the user based on haptic and/or tactile contact.Touch screen 112 and display controller 156 (along with any associatedmodules and/or sets of instructions in memory 102) detect contact (andany movement or breaking of the contact) on touch screen 112 andconverts the detected contact into interaction with user-interfaceobjects (e.g., one or more soft keys, icons, web pages or images) thatare displayed on touch screen 112. In an exemplary embodiment, a pointof contact between touch screen 112 and the user corresponds to a fingerof the user.

Touch screen 112 may use LCD (liquid crystal display) technology, LPD(light emitting polymer display) technology, or LED (light emittingdiode) technology, although other display technologies may be used inother embodiments. Touch screen 112 and display controller 156 maydetect contact and any movement or breaking thereof using any of aplurality of touch sensing technologies now known or later developed,including but not limited to capacitive, resistive, infrared, andsurface acoustic wave technologies, as well as other proximity sensorarrays or other elements for determining one or more points of contactwith touch screen 112. In an exemplary embodiment, projected mutualcapacitance sensing technology is used, such as that found in theiPhone®, iPod Touch®, and iPad® from Apple Inc. of Cupertino,California.

Touch screen 112 may have a video resolution in excess of 100 dpi. Insome embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user may make contact with touch screen 112using any suitable object or appendage, such as a stylus, a finger, andso forth. In some embodiments, the user interface is designed to workprimarily with finger-based contacts and gestures, which can be lessprecise than stylus-based input due to the larger area of contact of afinger on the touch screen. In some embodiments, the device translatesthe rough finger-based input into a precise pointer/cursor position orcommand for performing the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100 mayinclude a touchpad (not shown) for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad may be a touch-sensitive surface that is separatefrom touch screen 112 or an extension of the touch-sensitive surfaceformed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 may include a power management system, oneor more power sources (e.g., battery, alternating current (AC)), arecharging system, a power failure detection circuit, a power converteror inverter, a power status indicator (e.g., a light-emitting diode(LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 may also include one or more optical sensors 164. FIG. 1Ashows an optical sensor coupled to optical sensor controller 158 in I/Osubsystem 106. Optical sensor 164 may include charge-coupled device(CCD) or complementary metal-oxide semiconductor (CMOS)phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lens, and converts the lightto data representing an image. In conjunction with imaging module 143(also called a camera module), optical sensor 164 may capture stillimages or video. In some embodiments, an optical sensor is located onthe back of device 100, opposite touch screen display 112 on the frontof the device, so that the touch screen display may be used as aviewfinder for still and/or video image acquisition. In someembodiments, another optical sensor is located on the front of thedevice so that the user's image may be obtained for videoconferencingwhile the user views the other video conference participants on thetouch screen display.

Device 100 may also include one or more proximity sensors 166. FIG. 1Ashows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 may be coupled to input controller 160in I/O subsystem 106. In some embodiments, the proximity sensor turnsoff and disables touch screen 112 when the multifunction device isplaced near the user's ear (e.g., when the user is making a phone call).

Device 100 may also include one or more accelerometers 168. FIG. 1Ashows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 may be coupled to an input controller 160in I/O subsystem 106. In some embodiments, information is displayed onthe touch screen display in a portrait view or a landscape view based onan analysis of data received from the one or more accelerometers. Device100 optionally includes, in addition to accelerometer(s) 168, amagnetometer (not shown) and a GPS (or GLONASS or other globalnavigation system) receiver (not shown) for obtaining informationconcerning the location and orientation (e.g., portrait or landscape) ofdevice 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments memory 102 stores device/globalinternal state 157, as shown in FIGS. 1A and 3 . Device/global internalstate 157 includes one or more of: active application state, indicatingwhich applications, if any, are currently active; display state,indicating what applications, views or other information occupy variousregions of touch screen display 112; sensor state, including informationobtained from the device's various sensors and input control devices116; and location information concerning the device's location and/orattitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, oran embedded operating system such as VxWorks) includes various softwarecomponents and/or drivers for controlling and managing general systemtasks (e.g., memory management, storage device control, powermanagement, etc.) and facilitates communication between various hardwareand software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with the30-pin connector used on iPod (trademark of Apple Inc.) devices.

Contact/motion module 130 may detect contact with touch screen 112 (inconjunction with display controller 156) and other touch sensitivedevices (e.g., a touchpad or physical click wheel). Contact/motionmodule 130 includes various software components for performing variousoperations related to detection of contact, such as determining ifcontact has occurred (e.g., detecting a finger-down event), determiningif there is movement of the contact and tracking the movement across thetouch-sensitive surface (e.g., detecting one or more finger-draggingevents), and determining if the contact has ceased (e.g., detecting afinger-up event or a break in contact). Contact/motion module 130receives contact data from the touch-sensitive surface. Determiningmovement of the point of contact, which is represented by a series ofcontact data, may include determining speed (magnitude), velocity(magnitude and direction), and/or an acceleration (a change in magnitudeand/or direction) of the point of contact. These operations may beapplied to single contacts (e.g., one finger contacts) or to multiplesimultaneous contacts (e.g., “multitouch”/multiple finger contacts). Insome embodiments, contact/motion module 130 and display controller 156detect contact on a touchpad.

Contact/motion module 130 may detect a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns. Thus, a gesture may be detected by detecting a particularcontact pattern. For example, detecting a finger tap gesture includesdetecting a finger-down event followed by detecting a finger-up (liftoff) event at the same position (or substantially the same position) asthe finger-down event (e.g., at the position of an icon). As anotherexample, detecting a finger swipe gesture on the touch-sensitive surfaceincludes detecting a finger-down event followed by detecting one or morefinger-dragging events, and subsequently followed by detecting afinger-up (lift off) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the intensity of graphics that aredisplayed. As used herein, the term “graphics” includes any object thatcan be displayed to a user, including without limitation text, webpages, icons (such as user-interface objects including soft keys),digital images, videos, animations and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic may be assigned a corresponding code.Graphics module 132 receives, from applications etc., one or more codesspecifying graphics to be displayed along with, if necessary, coordinatedata and other graphic property data, and then generates screen imagedata to output to display controller 156.

Text input module 134, which may be a component of graphics module 132,provides soft keyboards for entering text in various applications (e.g.,contacts 137, e-mail 140, IM 141, browser 147, and any other applicationthat needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing, to camera 143 as picture/video metadata,and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 may include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   contacts module 137 (sometimes called an address book or contact        list);    -   telephone module 138;    -   video conferencing module 139;    -   e-mail client module 140;    -   instant messaging (IM) module 141;    -   workout support module 142;    -   camera module 143 for still and/or video images;    -   image management module 144;    -   browser module 147;    -   calendar module 148;    -   widget modules 149, which may include one or more of: weather        widget 149-1, stocks widget 149-2, calculator widget 149-3,        alarm clock widget 149-4, dictionary widget 149-5, and other        widgets obtained by the user, as well as user-created widgets        149-6;    -   widget creator module 150 for making user-created widgets 149-6;    -   search module 151;    -   video and music player module 152, which may be made up of a        video player module and a music player module;    -   notes module 153;    -   map module 154; and/or    -   online video module 155.

Examples of other applications 136 that may be stored in memory 102include other word processing applications, other image editingapplications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, and text input module 134, contactsmodule 137 may be used to manage an address book or contact list (e.g.,stored in application internal state 192 of contacts module 137 inmemory 102 or memory 370), including: adding name(s) to the addressbook; deleting name(s) from the address book; associating telephonenumber(s), e-mail address(es), physical address(es) or other informationwith a name; associating an image with a name; categorizing and sortingnames; providing telephone numbers or e-mail addresses to initiateand/or facilitate communications by telephone 138, video conference 139,e-mail 140, or IM 141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact module130, graphics module 132, and text input module 134, telephone module138 may be used to enter a sequence of characters corresponding to atelephone number, access one or more telephone numbers in address book137, modify a telephone number that has been entered, dial a respectivetelephone number, conduct a conversation and disconnect or hang up whenthe conversation is completed. As noted above, the wirelesscommunication may use any of a plurality of communications standards,protocols and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact module 130, graphics module132, text input module 134, contact list 137, and telephone module 138,videoconferencing module 139 includes executable instructions toinitiate, conduct, and terminate a video conference between a user andone or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, e-mail client module 140 includes executable instructions tocreate, send, receive, and manage e-mail in response to userinstructions. In conjunction with image management module 144, e-mailclient module 140 makes it very easy to create and send e-mails withstill or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages may include graphics, photos, audio files, video filesand/or other attachments as are supported in a MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, orIMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, text inputmodule 134, GPS module 135, map module 154, and music player module 146,workout support module 142 includes executable instructions to createworkouts (e.g., with time, distance, and/or calorie burning goals);communicate with workout sensors (sports devices); receive workoutsensor data; calibrate sensors used to monitor a workout; select andplay music for a workout; and display, store and transmit workout data.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, text input module 134, and cameramodule 143, image management module 144 includes executable instructionsto arrange, modify (e.g., edit), or otherwise manipulate, label, delete,present (e.g., in a digital slide show or album), and store still and/orvideo images.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, and text inputmodule 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, e-mail client module 140, and browser module 147, calendarmodule 148 includes executable instructions to create, display, modify,and store calendars and data associated with calendars (e.g., calendarentries, to do lists, etc.) in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, and browser module 147, widget modules 149 aremini-applications that may be downloaded and used by a user (e.g.,weather widget 149-1, stocks widget 149-2, calculator widget 149-3,alarm clock widget 149-4, and dictionary widget 149-5) or created by theuser (e.g., user-created widget 149-6). In some embodiments, a widgetincludes an HTML (Hypertext Markup Language) file, a CSS (CascadingStyle Sheets) file, and a JavaScript file. In some embodiments, a widgetincludes an XML (Extensible Markup Language) file and a JavaScript file(e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, and browser module 147, the widget creator module 150 may beused by a user to create widgets (e.g., turning a user-specified portionof a web page into a widget).

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, and text input module 134,search module 151 includes executable instructions to search for text,music, sound, image, video, and/or other files in memory 102 that matchone or more search criteria (e.g., one or more user-specified searchterms) in accordance with user instructions.

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, audio circuitry 110, speaker111, RF circuitry 108, and browser module 147, video and music playermodule 152 includes executable instructions that allow the user todownload and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present or otherwise play back videos (e.g., ontouch screen 112 or on an external, connected display via external port124). In some embodiments, device 100 may include the functionality ofan MP3 player, such as an iPod (trademark of Apple Inc.).

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, and text input module 134, notes module153 includes executable instructions to create and manage notes, to dolists, and the like in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, GPS module 135, and browser module 147, map module 154 maybe used to receive, display, modify, and store maps and data associatedwith maps (e.g., driving directions; data on landmarks such asbusinesses and other points of interest at or near a particularlocation; and other location-based data) in accordance with userinstructions.

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, audio circuitry 110, speaker111, RF circuitry 108, text input module 134, e-mail client module 140,and browser module 147, online video module 155 includes instructionsthat allow the user to access, browse, receive (e.g., by streamingand/or download), play back (e.g., on the touch screen or on anexternal, connected display via external port 124), send an e-mail witha link to a particular online video, and otherwise manage online videosin one or more file formats, such as H.264. In some embodiments, instantmessaging module 141, rather than e-mail client module 140, is used tosend a link to a particular online video.

Each of the above identified modules and applications correspond to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (i.e., sets of instructions) need notbe implemented as separate software programs, procedures or modules, andthus various subsets of these modules may be combined or otherwisere-arranged in various embodiments. In some embodiments, memory 102 maystore a subset of the modules and data structures identified above.Furthermore, memory 102 may store additional modules and data structuresnot described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 may be reduced.

The predefined set of functions that may be performed exclusivelythrough a touch screen and/or a touchpad include navigation between userinterfaces. In some embodiments, the touchpad, when touched by the user,navigates device 100 to a main, home, or root menu from any userinterface that may be displayed on device 100. In such embodiments, thetouchpad may be referred to as a “menu button.” In some otherembodiments, the menu button may be a physical push button or otherphysical input control device instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (in FIG. 1A) or 370 (FIG. 3 ) includes event sorter 170(e.g., in operating system 126) and a respective application 136-1(e.g., any of the aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripheral interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more views,when touch sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected may correspond to programmatic levels within aprogrammatic or view hierarchy of the application. For example, thelowest level view in which a touch is detected may be called the hitview, and the set of events that are recognized as proper inputs may bedetermined based, at least in part, on the hit view of the initial touchthat begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (i.e., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule, the hit view typically receives all sub-events related to thesame touch or input source for which it was identified as the hit view.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver module182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 may utilize or call data updater 176,object updater 177 or GUI updater 178 to update the application internalstate 192. Alternatively, one or more of the application views 191includes one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170, and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which may include sub-event delivery instructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch the eventinformation may also include speed and direction of the sub-event. Insome embodiments, events include rotation of the device from oneorientation to another (e.g., from a portrait orientation to a landscapeorientation, or vice versa), and the event information includescorresponding information about the current orientation (also calleddevice attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event 187 include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first lift-off (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second lift-off (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and lift-off of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event 187 alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers may interact with one another. In some embodiments, metadata183 includes configurable properties, flags, and/or lists that indicatewhether sub-events are delivered to varying levels in the view orprogrammatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module 145. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput-devices, not all of which are initiated on touch screens, e.g.,coordinating mouse movement and mouse button presses with or withoutsingle or multiple keyboard presses or holds, user movements taps,drags, scrolls, etc., on touch-pads, pen stylus inputs, movement of thedevice, oral instructions, detected eye movements, biometric inputs,and/or any combination thereof, which may be utilized as inputscorresponding to sub-events which define an event to be recognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screen maydisplay one or more graphics within user interface (UI) 200. In thisembodiment, as well as others described below, a user may select one ormore of the graphics by making a gesture on the graphics, for example,with one or more fingers 202 (not drawn to scale in the figure) or oneor more styluses 203 (not drawn to scale in the figure). In someembodiments, selection of one or more graphics occurs when the userbreaks contact with the one or more graphics. In some embodiments, thegesture may include one or more taps, one or more swipes (from left toright, right to left, upward and/or downward) and/or a rolling of afinger (from right to left, left to right, upward and/or downward) thathas made contact with device 100. In some embodiments, inadvertentcontact with a graphic may not select the graphic. For example, a swipegesture that sweeps over an application icon may not select thecorresponding application when the gesture corresponding to selection isa tap.

Device 100 may also include one or more physical buttons, such as “home”or menu button 204. As described previously, menu button 204 may be usedto navigate to any application 136 in a set of applications that may beexecuted on device 100. Alternatively, in some embodiments, the menubutton is implemented as a soft key in a GUI displayed on touch screen112.

In one embodiment, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, Subscriber Identity Module(SIM) card slot 210, head set jack 212, and docking/charging externalport 124. Push button 206 may be used to turn the power on/off on thedevice by depressing the button and holding the button in the depressedstate for a predefined time interval; to lock the device by depressingthe button and releasing the button before the predefined time intervalhas elapsed; and/or to unlock the device or initiate an unlock process.In an alternative embodiment, device 100 also may accept verbal inputfor activation or deactivation of some functions through microphone 113.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPU's) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320may include circuitry (sometimes called a chipset) that interconnectsand controls communications between system components. Device 300includes input/output (I/O) interface 330 comprising display 340, whichis typically a touch screen display. I/O interface 330 also may includea keyboard and/or mouse (or other pointing device) 350 and touchpad 355.Memory 370 includes high-speed random access memory, such as DRAM, SRAM,DDR RAM or other random access solid state memory devices; and mayinclude non-volatile memory, such as one or more magnetic disk storagedevices, optical disk storage devices, flash memory devices, or othernon-volatile solid state storage devices. Memory 370 may optionallyinclude one or more storage devices remotely located from CPU(s) 310. Insome embodiments, memory 370 stores programs, modules, and datastructures analogous to the programs, modules, and data structuresstored in memory 102 of portable multifunction device 100 (FIG. 1 ), ora subset thereof. Furthermore, memory 370 may store additional programs,modules, and data structures not present in memory 102 of portablemultifunction device 100. For example, memory 370 of device 300 maystore drawing module 380, presentation module 382, word processingmodule 384, website creation module 386, disk authoring module 388,and/or spreadsheet module 390, while memory 102 of portablemultifunction device 100 (FIG. 1 ) may not store these modules.

Each of the above identified elements in FIG. 3 may be stored in one ormore of the previously mentioned memory devices. Each of the aboveidentified modules corresponds to a set of instructions for performing afunction described above. The above identified modules or programs(i.e., sets of instructions) need not be implemented as separatesoftware programs, procedures or modules, and thus various subsets ofthese modules may be combined or otherwise re-arranged in variousembodiments. In some embodiments, memory 370 may store a subset of themodules and data structures identified above. Furthermore, memory 370may store additional modules and data structures not described above.

Attention is now directed towards embodiments of user interfaces (“UP”)that may be implemented on portable multifunction device 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces may be implemented on device300. In some embodiments, user interface 400 includes the followingelements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;

Battery status indicator 406;

-   -   Tray 408 with icons for frequently used applications, such as:        -   Phone 138, which may include an indicator 414 of the number            of missed calls or voicemail messages;        -   E-mail client 140, which may include an indicator 410 of the            number of unread e-mails;        -   Browser 147; and        -   Video and music player 152, also referred to as iPod            (trademark of Apple Inc.) module 152; and    -   Icons for other applications, such as:        -   IM 141;        -   Image management 144;        -   Camera 143;        -   Weather 149-1;        -   Stocks 149-2;        -   Workout support 142;        -   Calendar 148;        -   Alarm clock 149-4;        -   Map 154;        -   Notes 153;        -   Settings 412, which provides access to settings for device            100 and its various applications 136; and        -   Online video module 155, also referred to as YouTube            (trademark of Google Inc.) module 155.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3 ) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3 ) that is separate from the display 450 (e.g.,touch screen display 112). Although many of the examples which followwill be given with reference to inputs on touch screen display 112(where the touch sensitive surface and the display are combined), insome embodiments, the device detects inputs on a touch-sensitive surfacethat is separate from the display, as shown in FIG. 4B. In someembodiments the touch sensitive surface (e.g., 451 in FIG. 4B) has aprimary axis (e.g., 452 in FIG. 4B) that corresponds to a primary axis(e.g., 453 in FIG. 4B) on the display (e.g., 450). In accordance withthese embodiments, the device detects contacts (e.g., 460 and 462 inFIG. 4B) with the touch-sensitive surface 451 at locations thatcorrespond to respective locations on the display (e.g., in FIG. 4B, 460corresponds to 468 and 462 corresponds to 470). In this way, user inputs(e.g., contacts 460 and 462, and movements thereof) detected by thedevice on the touch-sensitive surface (e.g., 451 in FIG. 4B) are used bythe device to manipulate the user interface on the display (e.g., 450 inFIG. 4B) of the multifunction device when the touch-sensitive surface isseparate from the display. It should be understood that similar methodsmay be used for other user interfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse based input or stylus input).For example, a swipe gesture may be replaced with a mouse click (e.g.,instead of a contact) followed by movement of the cursor along the pathof the swipe (e.g., instead of movement of the contact). As anotherexample, a tap gesture may be replaced with a mouse click while thecursor is located over the location of the tap gesture (e.g., instead ofdetection of the contact followed by ceasing to detect the contact).Similarly, when multiple user inputs are simultaneously detected, itshould be understood that multiple computer mice may be usedsimultaneously, or a mouse and finger contacts may be usedsimultaneously.

User Interfaces and Associated Process

Attention is now directed towards embodiments of user interfaces (“UP”)and associated processes that may be implemented on an electronic devicewith a display and a touch-sensitive surface, such as device 300 orportable multifunction device 100.

FIGS. 5A-5K illustrate exemplary user interfaces for navigating throughinformation in a map-based interface in accordance with someembodiments. The user interfaces in these figures are used to illustratethe processes described below, including the processes in FIGS. 6A-6D.

FIG. 5A illustrates an exemplary user interface (“UP”) 500 of a mapapplication 154 displayed on touch screen 112 of device 100. UI 500 isdisplayed in a first mode (e.g., a map viewing mode) of the mapapplication; UI 500 displayed in the first mode is identified as UI500-A in the figures and in the description below. Geographic map 502 isdisplayed in UI 500-A at a first magnification level. Geographic map (or“map”) 502 at the first magnification level is labeled as geographic map502-A in the figures and in the description below. Geographic map 502may be displayed at any of a predefined range of magnification levels,and the first magnification level is one of the levels in the range.

In some embodiments, also displayed in UI 500 is magnification levelrange slider 508. Magnification level range slider 508 indicates thecurrent magnification level at which map 502 is displayed, relative tothe predefined range of magnification levels. A user may interact withslider 508 (e.g., by dragging the slider) to change the magnificationlevel of map 502 displayed in UI 500.

In some embodiments, map 502 may be an overhead (i.e., 90 degreesrelative to the ground) two-dimensional image (or multiple imagesarranged together), an overhead (i.e., 90 degrees relative to theground) satellite photo image (or multiple images arranged together), anangled (i.e., less than 90 degrees relative to the ground) map orsatellite photo image(s), or three-dimensional (3D) image(s).

Different types of geographic objects may be represented in map 502. Forexample, map 502-A includes landmarks 504 and streets 506. Examples oflandmarks 504 include buildings, designated or demarcated open areas(e.g., parks), monuments, etc. In map 502-A, landmarks 504 and streets506 are displayed as viewed from overhead.

Gesture 510 is detected on touch screen 112 at a location correspondingto landmark 504-A in map 502-A. Gesture 510 includes contacts (e.g.,finger contacts) 510-A and 510-B, both of which are at respectivelocations corresponding to landmark 504-A. In some embodiments, gesture510 is a multi-finger tap gesture (as shown in FIG. 5A). In some otherembodiments, gesture 510 is a depinch gesture; contacts 510-A and 510-Bmove apart from each other. In some further embodiments, gesture 510 isa single-finger tap gesture and gesture 510 has just one contact (e.g.,contact 510-A).

In response to the detection of gesture 510, geographic map 502 isdisplayed, in UI 500-A, at a second magnification level, different fromthe first magnification level, in the predefined range of magnificationlevels, as shown in FIG. 5B. Map 502 at the second magnification levelis identified as map 502-B. Landmark 504-A from map 502-A is displayedas landmark 504-B in map 502-B.

In some embodiments, the view shown by map 502-B is different from theview shown by map 502-A. For example, map 502-A shows a two-dimensionaloverhead view, and map 502-B shows an angled view. Landmark 504-A,displayed from an overhead view in map 502-A, is displayed as landmark504-B from an angle. Map 502-B may also include street 514,corresponding to a street 506 in map 502-A, displayed at an angle. Insome other embodiments, the map shown at the second magnification levelmaintains the view shown at the first magnification level (e.g., anoverhead view).

In FIG. 5B, gesture 516 is detected on touch screen 112 at a locationcorresponding to landmark 504-B. Gesture 516 includes contacts (e.g.,finger contacts) 516-A and 516-B, both of which are at respectivelocations corresponding to landmark 504-B. In some embodiments, gesture516 is a multi-finger tap gesture. In some other embodiments, thegesture 516 is a tap-and-hold gesture. In some further embodiments,gesture 516 is a depinch gesture; contacts 516-A and 516-B move apartfrom each other. In some further embodiments, gesture 516 is asingle-finger tap gesture and gesture 516 has just one contact (e.g.,contact 516-A).

In response to the detection of gesture 516, map application changes toa second mode (e.g., a landmark information mode), and UI 500 isdisplayed in the second mode, as shown in FIG. 5C. UI 500 in the secondmode is identified as UI 500-B. Map 502-B is displayed in UI 500-B.While displayed in UI 500-B, landmark 504-B is highlighted, becomingselected landmark 512. In some embodiments, selected landmark 512 isdisplayed as highlighted by displaying it in a different color thanlandmark 504-B, displayed with thicker or different colored borders (asin FIG. 5C), or displayed in some other way to visually distinguish itfrom landmark 504-B in the map viewing mode.

In some embodiments, the map application changes to the second mode inresponse to detection of a gesture if one or more predefined conditionsare satisfied when the gesture is detected. An example of a mode-changecondition is that the magnification level of map 502 is at a predefinedmagnification for changing to the second mode. For example, map 502-B inFIG. 5B is displayed at a predefined mode-change magnification level,and map 502-A in FIG. 5A is not displayed at the predefined mode-changemagnification level. Thus, the map application changes to the secondmode in response to the detection of gesture 516 but not gesture 510. Insome embodiments, the predefined mode-change magnification level is thehighest magnification level in the predefined range of magnificationlevels at which map 502 may be displayed.

Another example of a mode-change condition is that a contact in thegesture is maintained on the landmark to be selected for at least apredefined time (e.g., 0.5 second, 1 second, etc.). For example, in FIG.5B, if gesture 516 (where gesture 516 is a tap and hold gesture) isdetected on landmark 504-B for at least the predefined time, in responsethe map application changes to the second mode.

A further example of a mode-change condition is that there is a distinctsecond contact that is detected when a first contact in the gesture isdetected on the landmark to be selected. For example, gesture 516 hascontacts 516-A and 516-B that are both detected on landmark 504-B;contact 516-B satisfies the condition of the second contact. As anotherexample, if gesture 516 has just one contact 516-A, then contact 518(FIG. 5B) on map 502-B satisfies the condition of the second contact. Insome embodiments, contact 518 must be away from any landmark 504 in map502-B in order to satisfy the condition.

In FIG. 5C, gesture 520 is detected on touch screen 112 at a locationcorresponding to selected landmark 512 in map 502-B. Gesture 520includes contacts 520-A and 520-B. Contact 520-A and 520-B are movingaway from each other, in directions 522-A and 522-B respectively. Insome embodiments, gesture 520 is a depinch gesture.

In response to the detection of gesture 520, information 524 (FIG. 5E)about selected landmark 512 is displayed. In some embodiments, ananimation showing a transition from a display of selected landmark 512to a display of information 524 is displayed. For example, FIG. 5Ddepicts an instant in the animation transitioning from a display ofselected landmark 512 to a display of information 524. During theanimation, the information about selected landmark 512 appears onselected landmark 512 (e.g., if selected landmark 512 is a building, theinformation appears on a face of the building), and portions of selectedlandmark 512 fade out, become transparent, or otherwise become visuallyless prominent. For example, as the animation instance depicted in FIG.5D shows, the information is displayed on a face of selected landmark512 and the rest of selected landmark begin to fade out. The face ofselected landmark 512, which as shown is FIG. 5D is not parallel withthe plane of touch screen 112, transitions during the animation to apanel, with information 524, parallel with the plane of touch screen112, as shown in FIG. 5E. The faded selected landmark 512 may bedisplayed as faded landmark 525, or selected landmark 512 may cease tobe displayed entirely.

In some embodiments, gestures 516 (FIG. 5B) and 520 (FIG. 5C) arecontinuous with each other; there is no intervening lift-off of thefinger contact(s) between gestures 516 and 520. For example, if gesture516 is a tap and hold gesture on landmark 504-B (FIG. 5B), in responseto the detection of gesture 516, selected landmark 512 is displayed(FIG. 5C). Contacts 516-A and 516-B are maintained on selected landmark512; contacts 516-A and 516-B continue into gesture 520 as contacts520-A and 520-B (FIG. 5C). Contacts 520-A and 520-B move apart indirections 522-A and 522-B, respectively, in gesture 520. In response tothe detection of gesture 520, information 524 is displayed, as shown in,for example, FIG. 5E.

Any of a variety of information 524 about selected landmark 512 may bedisplayed in response to the detection of gesture 520. For example, ifselected landmark 512 is a building, information about the building,such as building floor and occupant information 524-A, may be displayed,as shown in FIG. 5E. As another example, if selected landmark 512 is apark, information about the park, such as the layout of park facilities,may be displayed.

For a selected landmark 512, information 524-B regarding persons who areassociated with selected landmark 512 may be displayed, as shown in FIG.5F. Information 524-B regarding persons associated with selectedlandmark 512 may include one or more users whose locations (or moreparticularly, the respective locations of devices associated with theusers) are being tracked (e.g., as friends of a user of device 100) toselected landmark 512 at the moment and their respective statuses (e.g.,available, busy, or any user-customized status designation from thetracked user). Information 524-B may include one or more persons who areassociated with selected landmark 512 or occupants of selected landmark512 (e.g., a person is an employee at a business at the selectedlandmark 512). In some embodiments, information regarding persons andtheir association with selected landmark 512 or its occupants arederived from user profiles (e.g., a social network profile, a userprofile associated with a device, or contact information) of thosepersons.

For a selected landmark 512, street-level view 524-C of selectedlandmark 512 may be displayed, as shown in FIG. 5G. Alternatively, apanoramic view 524-D from the perspective of selected landmark 512 maybe displayed, as shown in FIG. 5H.

When selected landmark 512 is a building, building floor and occupantinformation 524-A may be displayed, as described above and as shown inFIG. 5E. Alternatively, building floor and occupant information forselected landmark 512 may be displayed in building floor breakout 524-E,as shown in FIG. 5I. In some embodiments, floor breakout 524-E includesgraphical representations of the individual floors of selected landmark512, as well as labels on each floor representation identifying theoccupants of the respective floor.

In FIG. 5I, gesture 526 is detected on touch screen 112 at a locationcorresponding to floor breakout 524-E. Gesture 526 includes contacts526-A and 526-B. Contact 526-A and 526-B are moving away from eachother, in directions 528-A and 528-B respectively; gesture 526 is adepinch gesture.

In response to the detection of gesture 526, information for a singlefloor of the building may be displayed. In some embodiments, ananimation showing a transition from floor breakout 524-E to the singlefloor information is displayed. For example, the animation may show somefloors in floor breakout 524-E ceasing to be displayed, as the animationinstant depicted in FIG. 5J shows. When the animation is complete,single floor information for a floor in the building is displayed, asshown in FIG. 5K.

The single floor information may include floor plan information 524-Fand detailed floor information 524-G (e.g., additional details regardingthe floor occupant(s), users associated with the floor occupants, etc.)for a single floor. In some embodiments, the floor for which the singlefloor information is displayed may be iterated by successive gestures,such as successive depinch gestures. For example, in response to thedetection of a depinch gesture on floor breakout 524-E, single floorinformation for the first floor is displayed. In response to thedetection of a depinch gesture on the displayed single floor informationfor the first floor, single floor information for the second floor isdisplayed. In response to the detection of a depinch gesture on thedisplayed single floor information for the second floor, single floorinformation for the third floor is displayed, and so on.

As described above, a variety of information 524 for selected landmark512 may be displayed. Each kind of information 524 may be referred to asa level of information. For example, building floor and occupantinformation 524-A may be one level of information, associated usersinformation 524-B may be another level of information, single floorinformation for each floor is another level of information, and so on.In some embodiments, the levels of information may be iterated anddisplayed in accordance with a sequence in response to detection ofsuccessive gestures of the same type (e.g., depinch gestures). Forexample, in response to the detection of depinch gesture 520 on selectedlandmark 512 that is a building, building floor and occupant information524-A may displayed, as shown in FIG. 5E. In response to the detectionof a depinch gesture on building floor and occupant information 524-A,floor breakout 524-E may displayed. In response to the detection of adepinch gesture on floor breakout 524-E, single floor information (e.g.,floor plan information 524-F, detailed floor information 524-G) for thefirst floor may displayed. In response to the detection of a depinchgesture on the displayed single floor information for the first floor,single floor information for the second floor may displayed. In responseto the detection of a depinch gesture on the displayed single floorinformation for the second floor, single floor information for the thirdfloor may displayed, and so on. In response to the detection of adepinch gesture on the displayed single floor information for thehighest floor, associated persons information 524-B may be displayed,and so on. Eventually the sequence of levels of information loops backto floor breakout 524-E.

It should be appreciated that the sequence of levels of informationabove is merely exemplary. The sequence may include more or less levelsthan described above, including levels of information that are notdescribed in this specification. The levels may be ordered within thesequence in any suitable order.

Returning to FIG. 5K, gesture 532 is detected on touch screen 112 at alocation corresponding to the single floor information (in this case,detailed floor information 524-G). Gesture 532 includes contacts 530-Aand 530-B, at least one of which is on the single floor information(e.g., detailed floor information 524-G). Contacts 530-A and 530-B aremoving toward each other.

In response to the detection of gesture 532, information 524 aboutselected landmark 512 ceases to be displayed, and the map applicationreturns to the first mode (i.e., map 502-B is displayed in UI 500-A, asshown in FIG. 5B). In some embodiments, while map 502-B is displayed inUI 500-B (e.g., whenever any information 524 is displayed), the mapapplication returns to the first mode (i.e., map 502 is displayed in UI500-A) in response to the detection of a pinch gesture on touch screen112.

FIGS. 6A-6D are flow diagrams illustrating a method 600 of navigatingthrough information in a map-based interface in accordance with someembodiments. The method 600 is performed at an electronic device (e.g.,device 300, FIG. 3 , or portable multifunction device 100, FIG. 1 ) witha display and a touch-sensitive surface. In some embodiments, thedisplay is a touch screen display and the touch-sensitive surface is onthe display. In some embodiments, the display is separate from thetouch-sensitive surface. Some operations in method 600 may be combinedand/or the order of some operations may be changed.

As described below, the method 600 provides an intuitive way to navigatethrough information in a map-based interface. The method reduces thecognitive burden on a user when navigating through information in amap-based interface, thereby creating a more efficient human-machineinterface. For battery-operated electronic devices, enabling a user tonavigate through information in a map-based interface faster and moreefficiently conserves power and increases the time between batterycharges.

The device displays (602) a geographic map in a first mode of anapplication (e.g., map application 154 or other application containinggeographic information) on the display, the geographic map including aplurality of landmarks (e.g., buildings, parks, designated areas, orother physical locations), the geographic map being displayed at a firstmagnification level in a range of magnification levels. For example, map502-A is displayed in UI 500-A, as shown in FIG. 5A. Map 502-A isdisplayed at a first magnification level in a predefined range ofmagnification levels. Map 502-A includes one or more landmarks 504. Asanother example, map 502-B is displayed in UI 500-A, as shown in FIG.5B. Map 502-B is displayed at a second magnification level in thepredefined range of magnification levels. Map 502-B also includes one ormore landmarks 504.

The device detects (604) a first input on the touch-sensitive surface,the first input including a first finger contact at a location on thetouch-sensitive surface that corresponds to a first landmark on thedisplay. As shown in FIG. 5A, for example, gesture 510 is detected onlandmark 504-A. Gesture 510 includes at least one contact 510-A onlandmark 504-A. As another example, FIG. 5B shows gesture 516 beingdetected on landmark 504-B. Gesture 516 includes at least one contact516-A on landmark 504-B.

In some embodiments, the display is a touch-sensitive display thatincludes the touch-sensitive surface (606). For example, display 112(FIGS. 5A-5B) is a touch screen.

In some embodiments, the first input is a two-finger multitouch gesturemade with the first finger and a second finger that concurrentlycontacts the touch-sensitive surface (608). For example, gestures 510and 516 shown in FIGS. 5A and 5B, respectively, each have a secondconcurrent contact 510-B and 516-B, respectively.

In some embodiments, the first input is a single-finger tap gesture madewith the first finger (610). For example, gestures 510 and 516 shown inFIGS. 5A and 5B, respectively, may each be tap gestures with just onecontact 510-A and 516-A, respectively.

In response to detecting the first input on the touch-sensitive surface(612), when the first input does not satisfy one or more predefinedmode-change conditions, the device changes (614) the magnification levelof the geographic map in accordance with the first input and remains inthe first mode of the application. When the first input satisfies theone or more predefined mode-change conditions, the device selects (616)the first landmark and enters a second mode of the application that isdistinct from the first mode.

For example, in response to the detection of gesture 510, UI 500-A,corresponding to the first mode, continues to be displayed but map 502-Achanges magnification level and map 502-B is displayed (FIG. 5B). On theother hand, in response to the detection of gesture 516, UI 500-B isdisplayed and selected landmark 512 corresponding to landmark 504-B isdisplayed (FIG. 5C). In the case of gesture 510, the one or moremode-change conditions (e.g., map 502 being at a predefined mode-changemagnification level) were not satisfied when gesture 510 is detected.Conversely, in the case of gesture 516, the condition(s) were satisfied.

In some embodiments, the one or more predefined mode-change conditionsinclude that the first finger contact is maintained for at least apredefined time (e.g., 0.3, 0.5, 1.0, or 2.0 seconds) at a location onthe touch-sensitive surface that corresponds to the first landmark onthe display (618). For example, this condition is satisfied if, forgesture 510, at least contact 510-A is held at landmark 504-A (FIG. 5A)for at least the predefined time; selected landmark 512 would bedisplayed in map 502 (in either map 502-A or 502-B) in UI 500-B inresponse to gesture 510 (not shown). This condition is also satisfiedif, for gesture 516, at least contact 516-A is held at landmark 504-B(FIG. 5B) for at least the predefined time; selected landmark 512 isdisplayed in map 502 in UI 500-B in response to the detection of gesture516.

In some embodiments, the one or more predefined mode-change conditionsinclude that the first magnification is a predefined magnification forchanging to the second mode of the application (620) (e.g., a predefinedmagnification level at which a two-finger depinch gesture will result ina mode change, rather than a zoom-in or other magnifying operation). Forexample, as shown in FIGS. 5A-5B, map 502-A is not at the predefinedmagnification and map 502-B is at the predefined magnification. A modechange does not occur in response to the detection of a gesture 510 thatis a depinch gesture while map 502-A is displayed. In contrast, a modechange occurs in response to the detection of gesture 516 that is adepinch gesture while map 502-B is displayed.

In some embodiments, the one or more predefined mode-change conditionsinclude that a gesture by a second finger contact, distinct from thefirst finger contact, is detected while the first finger contact isdetected at the location on the touch-sensitive surface that correspondsto the first landmark on the display (622) (e.g., a tap gesture with thesecond finger). For example, the condition is satisfied if gesture 518is detected while contact 516-A is detected on landmark 504-B, as shownin FIG. 5B.

In some embodiments, when the first input satisfies the one or morepredefined mode-change conditions, the device visually highlights thefirst landmark (624) (e.g., displaying a border around the selectedlandmark or otherwise visually distinguishing the selected landmark inresponse to the first input). For example, selected landmark 512 in FIG.5C is displayed with thicker borders.

While in the second mode of the application, the device detects (626) asecond input on the touch-sensitive surface. For example, as shown inFIG. 5C, while selected landmark is displayed in UI 500-B (correspondingto the second mode), gesture 520 is detected.

In some embodiments, the first input is a two-finger multitouch gesturemade with the first finger and a second finger that concurrentlycontacts the touch-sensitive surface, and the second input is acontinuation of the first input (628) (e.g., a two-finger touch-and-holdgesture followed, without breaking contact with the touch-sensitivesurface, by a two-finger depinch gesture after the device enters thesecond mode). For example, gesture 516 includes contacts 516-A and516-B. Gesture 516 may be a tap and hold gesture that continues intodepinch gesture 520.

In some embodiments, the second input is a two-finger depinch gesture(630). For example, gesture 520 is depicted in FIG. 5C as a depinchgesture.

In response to detecting the second input on the touch-sensitivesurface, the device displays (632) information about the first landmark.As shown in FIG. 5E, for example, in response to the detection ofgesture 520, information 524 about selected landmark 512 correspondingto landmark 504-A is displayed.

In some embodiments, displaying information about the first landmark inresponse to detecting the second input includes displaying an animationof the first landmark transforming to the information about the firstlandmark (634). For example, in response to the detection of gesture520, an animation of selected landmark 512 transforming to information524-A about selected landmark 512 is displayed, as shown in FIGS. 5C-5E.

In some embodiments, the first landmark corresponds to a building, andthe information about the first landmark includes information aboutfloors of the building (636). For example, information 524-A depicted inFIG. 5E includes information about the floors of selected landmark 512.As another example, FIG. 5I shows floor breakout 524-E, which may bedisplayed in response to the detection of gesture 520.

In some embodiments, the information about the first landmark includes astreet-level view of the first landmark (638). FIG. 5G showsstreet-level view 524-C of selected landmark 512, which may be displayedin response to the detection of gesture 520.

In some embodiments, the information about the first landmark includes apanoramic view from a perspective of the first landmark (640). FIG. 5Hshows panoramic view 524-D from the perspective of selected landmark512, which may be displayed in response to the detection of gesture 520.

In some embodiments, the information about the first landmark includesinformation regarding associations between the first landmark and one ormore user profiles (642). For example, information 524-B regardingpersons who are associated with selected landmark 512 (FIG. 5F) mayinclude information regarding users who are associated with occupants ofselected landmark 512. Such information may be derived from userprofiles (e.g., if a user profile lists an occupant of selected landmark512 as a current employer).

In some embodiments, the information about the first landmark includesstatuses of users associated with the first landmark (644). For example,FIG. 5F shows information 524-B that indicates one or more users (e.g.,“John Doe,” “Jane Doe,” etc.) at selected landmark 512 with variousstatuses (e.g., “available,” “busy,” “eating,” etc.).

In some embodiments, while displaying information about the firstlandmark in the second mode of the application, the device detects (646)a third input (e.g., a two-finger depinch gesture at a location on thetouch sensitive surface that corresponds to the information about thefirst landmark).

In some embodiments, the second input and the third input are a sametype of gesture (648). For example, gesture 520 (FIG. 5C) and gesture526 (FIG. 5I) are both gestures of the same type.

In some embodiments, the second input and the third input are two-fingerdepinch gestures (650). For example, gesture 520 (FIG. 5C) and gesture526 (FIG. 5I) are both depinch gesture with two contacts.

In some embodiments, in response to detecting the third input (652), thedevice ceases to display (654) the information about the first landmark,and displays (656) additional information about the first landmark. Inother words, the information about the first landmark that is displayedin response to detecting the second input is replaced with otherinformation about the first landmark in response to detecting the thirdinput. For example, as shown in FIGS. 5I-5K, in response to thedetection of gesture 526, floor breakout 524-E is replaced with floorplan information 524-F and detailed floor information 524-G for a singlefloor.

In some embodiments, the first landmark corresponds to a building, theinformation about the first landmark includes information about floorsof the building, and the additional information about the first landmarkincludes information about a single floor of the building (658). Floorbreakout 524-E in FIG. 5I, for example, shows information about thefloors of selected landmark 512 where selected landmark 512 is abuilding. Floor plan information 524-F and detailed floor information524-G, shown in FIG. 5K shows information for a single floor forselected landmark 512 where selected landmark 512 is a building.

In some embodiments, the information about the single floor of thebuilding includes layout information for the single floor (660). Forexample, floor plan information 524-F shows the floor plan or layout fora floor of a building.

In some embodiments, in response to detecting the third input (652), thedevice displays (662) an animation of the information about the firstlandmark transitioning to the additional information about the firstlandmark. For example, FIGS. 5I-5K shows floor breakout 524-Etransitioning to floor plan information 524-F and detailed floorinformation 524-G.

In some embodiments, while displaying information about the firstlandmark in the second mode of the application, the device detects (664)a fourth input (e.g., a two-finger pinch gesture). In response todetecting the fourth input (666), the device ceases (668) to display theinformation about the first landmark, exits (670) the second mode of theapplication, and returns (672) to the first mode of the application. Forexample, as shown in FIG. 5K, while UI 500-B is displayed, gesture 532is detected. In response to the detection of gesture 532, floor planinformation 524-F and detailed floor information 524-G cease to bedisplayed, and the map application changes back to the first mode (e.g.,UI 500-B transitions to UI 500-A, as in FIG. 5B, and landmark 504-B isre-displayed).

It should be understood that the particular order in which theoperations in FIGS. 6A-6D have been described is merely exemplary and isnot intended to indicate that the described order is the only order inwhich the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein.

In accordance with some embodiments, FIG. 7 shows a functional blockdiagram of an electronic device 700 configured in accordance with theprinciples of the invention as described above. The functional blocks ofthe device may be implemented by hardware, software, or a combination ofhardware and software to carry out the principles of the invention. Itis understood by persons of skill in the art that the functional blocksdescribed in FIG. 7 may be combined or separated into sub-blocks toimplement the principles of the invention as described above. Therefore,the description herein may support any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 7 , an electronic device 700 includes a display unit702 configured to display a geographic map in a first mode of anapplication on the display unit 702, the geographic map including aplurality of landmarks, the geographic map being displayed at a firstmagnification level in a range of magnification levels; atouch-sensitive surface unit 704 configured to receive inputs andgestures; and a processing unit 706 coupled to the display unit 702 andthe touch-sensitive surface unit 704. In some embodiments, theprocessing unit 706 includes a detecting unit 708, a changing unit 710,a remaining unit 712, a selecting unit 714, an entering unit 716, adisplay enabling unit 718, a highlighting unit 720, a ceasing unit 722,an exiting unit 724, and a returning unit 726.

The processing unit 706 is configured to: detect a first input on thetouch-sensitive surface unit 704, the first input including a firstfinger contact at a location on the touch-sensitive surface unit 704that corresponds to a first landmark on the display unit 702 (e.g., withthe detecting unit 708); in response to detecting the first input on thetouch-sensitive surface unit 704: when the first input does not satisfyone or more predefined mode-change conditions, change the magnificationlevel of the geographic map in accordance with the first input (e.g.,with the changing unit 710) and remain in the first mode of theapplication (e.g., with the remaining unit 712); and when the firstinput satisfies the one or more predefined mode-change conditions,select the first landmark (e.g., with the selecting unit 714) and entera second mode of the application that is distinct from the first mode(e.g., with the entering unit 716); while in the second mode of theapplication, detect a second input on the touch-sensitive surface unit704 (e.g., with the detecting unit 708); and, in response to detectingthe second input on the touch-sensitive surface unit 704, enable displayof information about the first landmark (e.g., with the display enablingunit 718).

In some embodiments, the display unit 702 is a touch-sensitive displayunit 702 that includes the touch-sensitive surface unit 704.

In some embodiments, wherein the first input is a two-finger multitouchgesture made with the first finger and a second finger that concurrentlycontacts the touch-sensitive surface unit 704.

In some embodiments, wherein the first input is a two-finger multitouchgesture made with the first finger and a second finger that concurrentlycontacts the touch-sensitive surface unit 704, and the second input is acontinuation of the first input.

In some embodiments, wherein the first input is a single-finger tapgesture made with the first finger.

In some embodiments, wherein the one or more predefined mode-changeconditions include that the first finger contact is maintained for atleast a predefined time at a location on the touch-sensitive surfaceunit 704 that corresponds to the first landmark on the display unit 702.

In some embodiments, wherein the one or more predefined mode-changeconditions include that the first magnification is a predefinedmagnification for changing to the second mode of the application.

In some embodiments, wherein the one or more predefined mode-changeconditions include that a gesture by a second finger contact, distinctfrom the first finger contact, is detected while the first fingercontact is detected at the location on the touch-sensitive surface unit704 that corresponds to the first landmark on the display unit 702.

In some embodiments, wherein the processing unit 706 is configured to,when the first input satisfies the one or more predefined mode-changeconditions, visually highlight the first landmark (e.g., with thehighlighting unit 720).

In some embodiments, wherein the second input is a two-finger depinchgesture.

In some embodiments, wherein enabling display of information about thefirst landmark in response to detecting the second input includesenabling display of an animation of the first landmark transforming tothe information about the first landmark.

In some embodiments, the first landmark corresponds to a building, andthe information about the first landmark includes information aboutfloors of the building.

In some embodiments, the information about the first landmark includes astreet-level view of the first landmark.

In some embodiments, the information about the first landmark includes apanoramic view from a perspective of the first landmark.

In some embodiments, the information about the first landmark includesinformation regarding associations between the first landmark and one ormore user profiles.

In some embodiments, the information about the first landmark includesstatuses of users associated with the first landmark.

In some embodiments, the processing unit 706 is configured to: whiledisplaying information about the first landmark in the second mode ofthe application, detect a third input (e.g., with the detecting unit708); and, in response to detecting the third input: cease to displaythe information about the first landmark (e.g., with the ceasing unit722); and enable display of additional information about the firstlandmark (e.g., with the display enabling unit 718).

In some embodiments, the second input and the third input are a sametype of gesture.

In some embodiments, the second input and the third input are two-fingerdepinch gestures.

In some embodiments, the first landmark corresponds to a building, theinformation about the first landmark includes information about floorsof the building, and the additional information about the first landmarkincludes information about a single floor of the building.

In some embodiments, the information about the single floor of thebuilding includes layout information for the single floor.

In some embodiments, the processing unit 706 is configured to: inresponse to detecting the third input: enable display of an animation ofthe information about the first landmark transitioning to the additionalinformation about the first landmark (e.g., with the display enablingunit 718).

In some embodiments, the processing unit 706 is configured to: whiledisplaying information about the first landmark in the second mode ofthe application, detect a fourth input (e.g., with the detecting unit708); and, in response to detecting the fourth input: cease to displaythe information about the first landmark (e.g., with the ceasing unit722); exit the second mode of the application (e.g., with the exitingunit 724); and return to the first mode of the application (e.g., withthe returning unit 726).

The operations in the information processing methods described above maybe implemented by running one or more functional modules in informationprocessing apparatus such as general purpose processors or applicationspecific chips. These modules, combinations of these modules, and/ortheir combination with general hardware (e.g., as described above withrespect to FIGS. 1A and 3 ) are all included within the scope ofprotection of the invention.

The operations described above with reference to FIGS. 6A-6D may beimplemented by components depicted in FIGS. 1A-1B. For example,detection operations 604 and 626, changing and remaining operations 614,selecting and entering operations 616, and displaying operation 632 maybe implemented by event sorter 170, event recognizer 180, and eventhandler 190. Event monitor 171 in event sorter 170 detects a contact ontouch-sensitive display 112, and event dispatcher module 174 deliversthe event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface corresponds to apredefined event or sub-event, such as selection of an object on a userinterface. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 may utilize orcall data updater 176 or object updater 177 to update the applicationinternal state 192. In some embodiments, event handler 190 accesses arespective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the invention and its practical applications, to therebyenable others skilled in the art to best utilize the invention andvarious embodiments with various modifications as are suited to theparticular use contemplated.

What is claimed is:
 1. An electronic device, comprising: a display; oneor more processors; memory; and one or more programs, wherein the one ormore programs are stored in the memory and configured to be executed bythe one or more processors, the one or more programs includinginstructions for: displaying, on the display, a geographic map includinga representation of a first landmark; detecting a first input from auser of the electronic device at a location on the display correspondingto the representation of the first landmark; and in response todetecting the first input, displaying the geographic map, wherein thegeographic map includes: in accordance with a determination that a firstdevice associated with a first person different from the user of theelectronic device is physically located at the first landmark at themoment, information regarding the first person who is associated withthe first device physically located at the first landmark at the moment;and in accordance with a determination that a second device associatedwith a second person different from the user of the electronic device isphysically located at the first landmark at the moment, informationregarding the second person who is associated with the second devicephysically located at the first landmark at the moment.
 2. Theelectronic device of claim 1, wherein the information regarding thefirst person who is associated with the first device physically locatedat the first landmark at the moment and/or the information regarding thesecond person who is associated with the second device physicallylocated at the first landmark at the moment is displayed overlaying atleast a portion of the representation of the first landmark.
 3. Theelectronic device of claim 2, wherein the one or more programs furtherinclude instructions for: while displaying the information regarding thefirst person who is associated with the first device physically locatedat the first landmark at the moment and/or the information regarding thesecond person who is associated with the second device physicallylocated at the first landmark at the moment, displaying therepresentation of the first landmark with increased transparency.
 4. Theelectronic device of claim 1, wherein: the first person is determined tobe physically located at the first landmark at the moment based on thedetermination that the first device associated with the first person isphysically located at the first landmark when the first user input isdetected, and the second person is determined to be physically locatedat the first landmark at the moment based on the determination that thesecond device associated with the second person is physically located atthe first landmark when the first user input is detected.
 5. Theelectronic device of claim 1, wherein the first landmark is associatedwith a business, and wherein one or more persons who are associated withthe first landmark include one or more employees of the business.
 6. Theelectronic device of claim 1, wherein the one or more programs furtherinclude instructions for: determining that the first person isphysically located at the first landmark at the moment based on a userprofile of the first person.
 7. The electronic device of claim 1,wherein: the information regarding the first person who is associatedwith the first device physically located at the first landmark at themoment includes a status of the first person; and the informationregarding the second person who is associated with the second devicephysically located at the first landmark at the moment includes a statusof the second person.
 8. The electronic device of claim 1, wherein thefirst landmark includes at least one of a building, a designated openarea, a demarcated open area, a park, or a monument.
 9. A non-transitorycomputer-readable storage medium storing one or more programs configuredto be executed by one or more processors of an electronic device with adisplay, the one or more programs including instructions for:displaying, on the display, a geographic map including a representationof a first landmark; detecting a first input from a user of theelectronic device at a location on the display corresponding to therepresentation of the first landmark; and in response to detecting thefirst input, displaying the geographic map, wherein the geographic mapincludes: in accordance with a determination that a first deviceassociated with a first person different from the user of the electronicdevice is physically located at the first landmark at the moment,information regarding the first person who is associated with the firstdevice physically located at the first landmark at the moment; and inaccordance with a determination that a second device associated with asecond person different from the user of the electronic device isphysically located at the first landmark at the moment, informationregarding the second person who is associated with the second devicephysically located at the first landmark at the moment.
 10. Thenon-transitory computer-readable storage medium of claim 9, wherein theinformation regarding the first person who is associated with the firstdevice physically located at the first landmark at the moment and/or theinformation regarding the second person who is associated with thesecond device physically located at the first landmark at the moment isdisplayed overlaying at least a portion of the representation of thefirst landmark.
 11. The non-transitory computer-readable storage mediumof claim 10, wherein the one or more programs further includeinstructions for: while displaying the information regarding the firstperson who is associated with the first device physically located at thefirst landmark at the moment and/or the information regarding the secondperson who is associated with the second device physically located atthe first landmark at the moment, displaying the representation of thefirst landmark with increased transparency.
 12. The non-transitorycomputer-readable storage medium of claim 9, wherein: the first personis determined to be physically located at the first landmark at themoment based on the determination that the first device associated withthe first person is physically located at the first landmark when thefirst user input is detected, and the second person is determined to bephysically located at the first landmark at the moment based on thedetermination that the second device associated with the second personis physically located at the first landmark when the first user input isdetected.
 13. The non-transitory computer-readable storage medium ofclaim 9, wherein the first landmark is associated with a business, andwherein one or more persons who are associated with the first landmarkinclude one or more employees of the business.
 14. The non-transitorycomputer-readable storage medium of claim 9, wherein the one or moreprograms further include instructions for: determining that the firstperson is physically located at the first landmark at the moment basedon a user profile of the first person.
 15. The non-transitorycomputer-readable storage medium of claim 9, wherein: the informationregarding the first person who is associated with the first devicephysically located at the first landmark at the moment includes a statusof the first person; and the information regarding the second person whois associated with the second device physically located at the firstlandmark at the moment includes a status of the second person.
 16. Thenon-transitory computer-readable storage medium of claim 9, wherein thefirst landmark includes at least one of a building, a designated openarea, a demarcated open area, a park, or a monument.
 17. A method,comprising: at an electronic device with a display: displaying, on thedisplay, a geographic map including a representation of a firstlandmark; detecting a first input from a user of the electronic deviceat a location on the display corresponding to the representation of thefirst landmark; and in response to detecting the first input, displayingthe geographic map, wherein the geographic map includes: in accordancewith a determination that a first device associated with a first persondifferent from the user of the electronic device is physically locatedat the first landmark at the moment, information regarding the firstperson who is associated with the first device physically located at thefirst landmark at the moment; and in accordance with a determinationthat a second device associated with a second person different from theuser of the electronic device is physically located at the firstlandmark at the moment, information regarding the second person who isassociated with the second device physically located at the firstlandmark at the moment.
 18. The method of claim 17, wherein theinformation regarding the first person who is associated with the firstdevice physically located at the first landmark at the moment and/or theinformation regarding the second person who is associated with thesecond device physically located at the first landmark at the moment isdisplayed overlaying at least a portion of the representation of thefirst landmark.
 19. The method of claim 18, further comprising: whiledisplaying the information regarding the first person who is associatedwith the first device physically located at the first landmark at themoment and/or the information regarding the second person who isassociated with the second device physically located at the firstlandmark at the moment, displaying the representation of the firstlandmark with increased transparency.
 20. The method of claim 17,wherein: the first person is determined to be physically located at thefirst landmark at the moment based on the determination that the firstdevice associated with the first person is physically located at thefirst landmark when the first user input is detected, and the secondperson is determined to be physically located at the first landmark atthe moment based on the determination that the second device associatedwith the second person is physically located at the first landmark whenthe first user input is detected.
 21. The method of claim 17, whereinthe first landmark is associated with a business, and wherein one ormore persons who are associated with the first landmark include one ormore employees of the business.
 22. The method of claim 17, wherein themethod further comprises: determining that the first person isphysically located at the first landmark at the moment based on a userprofile of the first person.
 23. The method of claim 17, wherein: theinformation regarding the first person who is associated with the firstdevice physically located at the first landmark at the moment includes astatus of the first person; and the information regarding the secondperson who is associated with the second device physically located atthe first landmark at the moment includes a status of the second person.24. The method of claim 17, wherein the first landmark includes at leastone of a building, a designated open area, a demarcated open area, apark, or a monument.